Skip to content

fix(cli): drop unsupported --no-banner flag for copilotkit v2#1633

Open
and-human wants to merge 1 commit into
ag-ui-protocol:mainfrom
and-human:fix/cli-copilotkit-v2-no-banner
Open

fix(cli): drop unsupported --no-banner flag for copilotkit v2#1633
and-human wants to merge 1 commit into
ag-ui-protocol:mainfrom
and-human:fix/cli-copilotkit-v2-no-banner

Conversation

@and-human
Copy link
Copy Markdown

Summary

copilotkit@2.0.0 (released ~3 days ago) rewrote the CopilotKit CLI and removed the --no-banner flag. create-ag-ui-app still passes that flag to the spawned npx copilotkit@latest create, which now aborts with Unknown option '--no-banner' whenever a user picks CopilotKit/Next.js. This PR drops the unsupported flag from the spawn argv.

Reproduction (from #1627)

$ npx create-ag-ui-app@latest

   █████╗  ██████╗       ██╗   ██╗ ██╗
  ...
  Agent User Interactivity Protocol

✔ What client do you want to use? CopilotKit/Next.js
✔ What would you like to name your project? my-ag-ui-app
(node:3653) [DEP0190] DeprecationWarning: Passing args to a child process with shell option true ...
Unknown option '--no-banner'

❌ Project creation failed.

Fix

   const copilotkit = spawn("npx",
     [
       "copilotkit@latest",
       "create",
-      "--no-banner",
       "-n", projectName.name,
       ...frameworkArgs,
     ],

sdks/typescript/packages/cli/src/index.ts, inside handleCopilotKitNextJs(). One-line removal.

Backward compatibility

The spawn target is hard-coded to copilotkit@latest, so users always resolve to the latest dist-tag.

  • copilotkit ≥ 2.0.0 (current latest, what was broken): fixed.
  • copilotkit 1.x: --no-banner was a cosmetic -q, --no-banner that suppressed the banner. Removing the flag means CopilotKit's banner now prints during nested creation — harmless. In practice this path is unreachable since @latest no longer resolves to 1.x.

No replacement flag exists in v2 (copilotkit create v2 only accepts -n -i -f -h).

Testing

  • pnpm --filter create-ag-ui-app build — clean
  • pnpm --filter create-ag-ui-app typecheck — clean
  • pnpm --filter create-ag-ui-app test:exports (publint --strict + attw) — clean
  • End-to-end smoke: ran the locally-built CLI with --mastra, scaffolding completed successfully against current copilotkit@latest (project smoke-test created, no Unknown option error).

Out of scope (separate follow-up)

Noticed while reading the file: line 113 reads options.crewiAiFlows while line 43 declares the flag as crewaiFlows (typo: crewi vs crewai). CrewAI Flows scaffolding via the framework flag is silently broken — happy to file a follow-up issue/PR after this one merges.

Fixes #1627

copilotkit@2.0.0 rewrote its CLI and removed --no-banner. The
create-ag-ui-app scaffolder still passes the flag to
`npx copilotkit@latest create`, causing
"Unknown option '--no-banner'" and aborting project creation
whenever a user picks CopilotKit/Next.js.

The flag was cosmetic in v1 (banner suppression only) and has
no v2 replacement, so removing it is sufficient. The CopilotKit
banner now prints during nested creation, which is harmless.

Fixes ag-ui-protocol#1627
@and-human and-human requested a review from a team as a code owner May 5, 2026 11:46
@vercel
Copy link
Copy Markdown

vercel Bot commented May 5, 2026

@and-human is attempting to deploy a commit to the CopilotKit Team on Vercel.

A member of the Team first needs to authorize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Build applications > Automatic Setup not working with last copilotkit / nextjs version

1 participant